In my implementation, I only require the use of OData with GET requests. However, Lodata registers a Route::any by default, which intercepts all HTTP methods.
This causes conflicts when trying to define standard routes for other methods (e.g., POST, PUT, DELETE) since they are routed to Lodata due to the shared prefix between the API and Lodata routes.

To resolve this, I've introduced a getter and setter in the model that determines whether a route should be registered.
This property defaults to true, providing flexibility in controlling which routes are handled by Lodata and enabling the ability to override the base route.

Example Usage:

In AppServiceProvider:
Add the following line inside the boot() method to stop Lodata from automatically registering routes:

Lodata::ignoreRoutes();

In api.php:
Define a specific GET route for OData requests:

Route::get('{path}', [OData::class, 'handle'])->where('path', '(.*)');